🐛 [Frontend] Fix: Crop long parameter values #8393
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
odeimaiz
added
bug
|
odeimaiz
requested review from
GitHK,
bisgaard-itis,
giancarloromeo,
matusdrobuliak66,
mguidon,
pcrespov,
sanderegg and
wvangeit
matusdrobuliak66
approved these changes
Sep 19, 2025
Contributor
🧪 CI InsightsHere's what we observed from your CI run for 8c08f68. ✅ Passed Jobs With Interesting Signals
|
wvangeit
approved these changes
Sep 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
reported by @wvangeit
When the value of a parameter node is too long, its representation on the NodeUI isn't cut, making the node output pin hidden. This PR fixes this situation by cropping the string and showing an ellipses.
Bonus
Before:
After:
Bonus, Collaborators:
Related issue/s
How to test
Dev-ops